-
Notifications
You must be signed in to change notification settings - Fork 81
[HOLD] AAP-45875 Runtime Feature Flags #736
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Conversation
3822dfe
to
6b72afd
Compare
081fdcc
to
f492546
Compare
3699be8
to
8b6d0bc
Compare
fedaa23
to
69f6bbb
Compare
9860248
to
5b7f1f9
Compare
Downstream failures, starting to hit the database for references like this in AWX:
These are probably expected. This is in the job execution path, so that's not too big of a deal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with the decisions made here, totally ready to 👍 this
Almost all my comments are to improve documentation, very simple things.
I'm just unclear if the API endpoints (views, serializers) are finished. I'm confused about that, in terms of what the UI needs to be delivered with this, what the response looks like, and if that's planned for later or anything.
5b7f1f9
to
dfb2ec7
Compare
Hey @AlanCoding, Thanks for the feedback. I just updated to address all of these notes. Regarding your comments -
|
37a9a34
to
79da99f
Compare
79da99f
to
1e9b6aa
Compare
DVCS PR Check Results: PR appears valid (JIRA key(s) found) |
|
Description
https://issues.redhat.com/browse/AAP-45875
This change is the foundation for enabling runtime platform feature flags for AAP. This updates the django-ansible-base to be the central location where all platform flags are defined. Components can inherit the
ansible_base.feature_flags
application to inherit all platform feature flag definitions.To enable runtime platform feature flags in AAP.
This change addresses the issue by defining a database flag source, which contains all the feature flags along with their associated metadata.
These feature flags are installed into each components database at install-time and kept in sync via resource sync (Gateway is the provider)
Before this can be merged, the following should be done -
Type of Change
Self-Review Checklist
Testing Instructions
Prerequisites
Steps to Test
Recommend testing this through AAP Dev, but it can be tested directly via the test app as well.
make configure-sources
Expected Results
AAP Deploys as expected with database feature flags.
Notes
This PR is the prerequisite for the following component PRs -
Gateway - https://github.com/ansible/aap-gateway/pull/795
EDA - ansible/eda-server#1346
Galaxy - ansible/galaxy_ng#2615
AWX - ansible/awx#16030